home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.cs.arizona.edu
/
ftp.cs.arizona.edu.tar
/
ftp.cs.arizona.edu
/
icon
/
newsgrp
/
group94b.txt
/
000027_icon-group-sender _Tue Aug 30 12:06:06 1994.msg
< prev
next >
Wrap
Internet Message Format
|
1995-02-09
|
2KB
Received: by cheltenham.cs.arizona.edu; Tue, 30 Aug 1994 11:26:38 MST
To: icon-group-l@cs.arizona.edu
Date: 30 Aug 1994 12:06:06 -0400
From: nmw@ios.com (Nick Williams)
Message-Id: <33vlde$95i@ios.com>
Organization: Internet Online Services
Sender: icon-group-request@cs.arizona.edu
References: <33t025$ba5@highway.leidenuniv.nl>, <33tacj$pen@ios.com>, <1994Aug30.140940.5002@midway.uchicago.edu>
Subject: Re: Icon - still alive??
Errors-To: icon-group-errors@cs.arizona.edu
In article <1994Aug30.140940.5002@midway.uchicago.edu>,
Richard L. Goerwitz <goer@midway.uchicago.edu> wrote:
>In article <33tacj$pen@ios.com> nmw@ios.com (Nick Williams) writes:
>>
>>Yes, and I should correct my previous statement: I use it for small
>>tasks because I don't have lots of data to analyse, but do some bit of
>>systems programming, for which Icon is not suited very well just yet...
>>(One of my dreams is to write an httpd in Icon...)
>Just yet?
>That's funny. I feel quite the opposite. I dread the kitchen sink
>mentality - turning Icon into a heap of platform-specific extensions
>geared for things that C and PERL already do much better.
I could deal with loadfunc really (as one of the examples in the IPL
demonstrates), but some things (setenv() comes to mind...) should be
standard. If the presence of more system dependent features makes Icon
programs non-portable, then they can be put in separate libraries along
with LARGE warnings in the documentation; if someone uses them and gets
stuck with non-portable code, then so be it, after all, they'd have seen
the warnings.
As for C and Perl, I love C, and hate Perl, but Icon can save me a lot
of work if I can use it instead of C for certain problems.
>Fight feeping creaturism!
>--
> -Richard L. Goerwitz goer%midway@uchicago.bitnet
> goer@midway.uchicago.edu rutgers!oddjob!ellis!goer
Nick
PS: let's not deteriorate into a comp.lang.lisp style language war.